IRIX Base Documentation 2001 May

home *** CD-ROM | disk | FTP | other *** search

/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / relnotes / sitemgr / ch2.z / ch2

Wrap

Text File | 2001-04-17 | 24KB | 526 lines

- 1 - 2. _I_n_s_t_a_l_l_a_t_i_o_n__I_n_f_o_r_m_a_t_i_o_n This chapter lists supplemental information to the _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e. The information listed here is product- and release-specific; use it with the Installation Guide to install this product. 2.1 _S_i_t_e_M_g_r__S_u_b_s_y_s_t_e_m_s SiteMgr includes these subsystems: _s_i_t_e_m_g_r._b_o_o_k_s._S_i_t_e_M_g_r__U_G SiteMgr User's Guide, 1.1 _s_i_t_e_m_g_r._m_a_n._m_a_n_p_a_g_e_s SiteMgr Man Pages, 1.1 _s_i_t_e_m_g_r._m_a_n._r_e_l_n_o_t_e_s SiteMgr Release Notes, 1.1 _s_i_t_e_m_g_r._s_w._b_a_s_e SiteMgr Base Software, 1.1 _s_i_t_e_m_g_r._s_w._c_l_i_e_n_t SiteMgr Client Software, 1.1 _s_i_t_e_m_g_r._s_w._s_e_r_v_e_r SiteMgr Server Extensions Software, 1.1 2.2 _S_i_t_e_M_g_r__S_u_b_s_y_s_t_e_m__D_i_s_k__S_p_a_c_e__R_e_q_u_i_r_e_m_e_n_t_s This section lists the subsystems (and their sizes) of SiteMgr. If you are installing this product for the first time, the subsystems marked ``default'' are the ones that are installed if you use the ``go'' menu item. To install a different set of subsystems, use the ``install,'' ``remove,'' ``keep,'' and ``step'' commands in _i_n_s_t to customize the list of subsystems to be installed, then select the ``go'' menu item. Note: The listed subsystem sizes are approximate. Refer to the _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for information on finding exact sizes. Subsystem Name Subsystem Size (Kilobytes) _s_i_t_e_m_g_r._b_o_o_k_s._S_i_t_e_M_g_r__U_G (default) 764 _s_i_t_e_m_g_r._m_a_n._m_a_n_p_a_g_e_s (default) 24 _s_i_t_e_m_g_r._m_a_n._r_e_l_n_o_t_e_s (default) 48 - 2 - _s_i_t_e_m_g_r._s_w._b_a_s_e (default) 276 _s_i_t_e_m_g_r._s_w._c_l_i_e_n_t (default) 2120 _s_i_t_e_m_g_r._s_w._s_e_r_v_e_r 856 2.3 _I_n_s_t_a_l_l_a_t_i_o_n__M_e_t_h_o_d All of the subsystems for SiteMgr can be installed using IRIX. You do not need to use the miniroot. Refer to the _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for complete installation instructions. 2.4 _P_r_e_r_e_q_u_i_s_i_t_e_s _s_i_t_e_m_g_r._s_w._c_l_i_e_n_t requires that _w_e_b_v_i_e_w_e_r._s_w._e_o_e and _w_e_b_s_u_p_p_o_r_t__e_o_e._s_w._l_i_b (version 1.2 or greater), are installed. _w_e_b_v_i_e_w_e_r._s_w._e_o_e requires _i_f_l__e_o_e._s_w._c++, version 1.2 or greater, to be installed as well. _s_i_t_e_m_g_r._s_w._s_e_r_v_e_r requires that _w_e_b_s_u_p_p_o_r_t__e_o_e._s_w._l_i_b (version 1.2 or greater) be installed. Also, if you are running a Netscape FastTrack Personal Server, version 2.0P (_n_s__f_a_s_t_t_r_a_c_k) or earlier, and intend to utilize the SiteMgr Server Extensions in conjunction with that server, you should upgrade to (at least) version 2.01 (of _n_s__f_a_s_t_t_r_a_c_k). In earlier versions of this server there were problems handling CGI (Common Gateway Interface) processes which could cause the SiteMgr client to get into a "hung" state. Version 2.01 of the Netscape FastTrack Personal Server can be found on the IRIX 6.5 Applications CD, or on the IRIX Applications CD (for IRIX 6.2, 6.3 and 6.4) which was released in August of 1997. If you will be using version control in SiteMgr, you will need to install _e_o_e._s_w._r_c_s (the Revision Control System Utilities), if this subsystem is not already installed on the server machine. If you wish to enable the spell checking feature now available for the Validation module, you will need to install _e_o_e._s_w._s_p_e_l_l (the Spell Utilities), if this subsystem is not already installed on the server machine. - 3 - 2.5 _C_o_m_p_a_t_i_b_i_l_i_t_y When upgrading from an earlier version of SiteMgr, the web site database that was previously built by the SiteMgr initialization process will need to be upgraded. This operation can be done easily from within the SiteMgr client, when you first attempt to load the particular web site (you will be prompted accordingly). However, before this operation can happen, the server machine that contains the SiteMgr database (the machine/web site being administered by SiteMgr) _m_u_s_t be upgraded with the latest SiteMgr software, in particular, _s_i_t_e_m_g_r._s_w._b_a_s_e and _s_i_t_e_m_g_r._s_w._s_e_r_v_e_r, version 1.1 (the version of the Server Extensions and the Client _m_u_s_t match). 2.6 _O_t_h_e_r__I_n_s_t_a_l_l_a_t_i_o_n__I_n_f_o_r_m_a_t_i_o_n 2.6.1 _E_n_a_b_l_i_n_g__a__H_T_T_P__S_e_r_v_e_r__F_o_r__S_i_t_e_M_g_r To enable your web site for use with SiteMgr, the server software must be installed. Follow this procedure in inst(1M) on your server machine: IIIInnnnsssstttt>>>> iiiinnnnssssttttaaaallllllll ssssiiiitttteeeemmmmggggrrrr....sssswwww....bbbbaaaasssseeee ssssiiiitttteeeemmmmggggrrrr....sssswwww....sssseeeerrrrvvvveeeerrrr After installation, the SiteMgr client can now communicate through HTTP with three SIteMgr CGI (Common Gateway Interface) processes. By default, links are created from these processes into the default CGI directory, /_v_a_r/_w_w_w/_c_g_i-_b_i_n. If your HTTP server initiates CGI processes from some other directory, you need to create these links manually: #### ccccdddd <<<<ddddeeeeffffaaaauuuulllltttt____HHHHTTTTTTTTPPPP____sssseeeerrrrvvvveeeerrrr____CCCCGGGGIIII____ddddiiiirrrreeeeccccttttoooorrrryyyy>>>> #### llllnnnn ----ssss ////uuuussssrrrr////ssssiiiitttteeeemmmmggggrrrr////bbbbiiiinnnn////ssssiiiitttteeeemmmmggggrrrr....ccccggggiiii .... #### llllnnnn ----ssss ////uuuussssrrrr////ssssiiiitttteeeemmmmggggrrrr////bbbbiiiinnnn////ssssiiiitttteeeessssttttaaaatttt....ccccggggiiii .... #### llllnnnn ----ssss ////uuuussssrrrr////ssssiiiitttteeeemmmmggggrrrr////bbbbiiiinnnn////ssssmmmmddddbbbbffff....ccccggggiiii .... At this point, you should be able to communicate with these processes utilizing the SiteMgr client (_s_i_t_e_m_g_r(1)). A database will be created automatically for you on the HTTP server instance which will monitor your web site documents and apply revision control, if so desired. _N_O_T_E: We _s_t_r_o_n_g_l_y _r_e_c_o_m_m_e_n_d that you provide a secure server environment for SiteMgr. We advise you to carefully read over the next section, "Security and - 4 - SiteMgr." It is important to note that after the database is initialized, anyone with Web access to the SiteMgr http server can write to your site. It is _s_t_r_o_n_g_l_y _r_e_c_o_m_m_e_n_d_e_d that you configure that server's authorization features so that password protection and/or domain restrictions apply. 2.6.2 _S_e_c_u_r_i_t_y__a_n_d__S_i_t_e_M_g_r Because the SiteMgr CGI processes can be used to publish documents, remove documents, etc.; we _s_t_r_o_n_g_l_y _r_e_c_o_m_m_e_n_d that you provide a secure server environment for SiteMgr to run in. To fully utilize SiteMgr for publishing, your HTTP server must be run under a user ID that can perform such operations (modifying, removing, etc.) on your web site files, under the document root that is being administered by SiteMgr. Refer to your HTTP server configuration files to see if this is being done. For example, your server can be changed to run as user _s_g_i_w_e_b instead of _n_o_b_o_d_y. The permissions of the files in your document root must allow write access for user _s_g_i_w_e_b. This could done by making _s_g_i_w_e_b the owner of those files or by making the files group-writable and ensuring that _s_g_i_w_e_b is in the correct group. You may also wish to create a unique HTTP server instance (different port) to access the SiteMgr CGI processes. That instance could be run under a user ID that can perform the aforementioned operations. Another option, utilizing this same methodology, is to only invoke/start this server when needed, rather than keeping it constantly running. It is also strongly recommended (but not required) to use your HTTP server's authorization feature to apply a password and user combination onto both SiteMgr CGI processes. Refer to your server documentation for specifics on how to set this up. If you are using a Netscape Server and the Netscape Administration Server supports the use of ACL's (Access Control Lists), refer to the following brief scenario on how to establish security for the SiteMgr CGI processes: +o Run the Netscape Administration Server (see _n_s- _a_d_m_i_n(1M) for details) and connect via standard - 5 - browser. +o Create two unique users, each with their own unique password. The reason you may want to create two is due to the specific functionality of the SiteMgr CGI's. The database creation/update CGI (_s_m_d_b_f._c_g_i(1)), which is not run as often, may have a higher level of restriction/security assigned to it than the standard SiteMgr CGI's (_s_i_t_e_m_g_r._c_g_i(1) and _s_i_t_e_s_t_a_t._c_g_i(1)). +o _R_e_s_t_r_i_c_t _a_c_c_e_s_s to the SiteMgr CGI's. For example, if your default CGI directory is /var/www/cgi-bin; access should be restricted to /var/www/cgi-bin/sitemgr.cgi, /var/www/cgi-bin/sitestat.cgi, and /var/www/cgi- bin/smdbf.cgi. For each, set the appropriate _P_e_r_m_i_s_s_i_o_n_s. The _A_c_c_e_s_s _T_y_p_e for both Read and Write should be set to "Deny". +o Write out your changes and restart your Netscape Server instance using the Netscape Administration Server functionality. For an earlier Netscape Server, or one which does not utilize ACL's (Access Control Lists), the following steps can be performed: +o Run the Netscape Administration Server, connect via standard browser. +o Create two user/password authentication databases, each with a unique password and user combination. You may wish to create two, since the database creation/update CGI (_s_m_d_b_f._c_g_i(1)), which is not run as often, may have a higher level of restriction/security assigned to it than the standard SiteMgr CGI's (_s_i_t_e_m_g_r._c_g_i(1) and _s_i_t_e_s_t_a_t._c_g_i(1)). +o Modify the HTTP server instance configuration file, _o_b_j._c_o_n_f and add the following (provided as example only; modify paths, etc. for your environment) lines: <<<<OOOObbbbjjjjeeeecccctttt ppppppppaaaatttthhhh====""""////vvvvaaaarrrr////wwwwwwwwwwww////ccccggggiiii----bbbbiiiinnnn////ssssiiiitttteeeemmmmggggrrrr....****"""">>>> AAAAuuuutttthhhhTTTTrrrraaaannnnssss ffffnnnn====""""bbbbaaaassssiiiicccc----nnnnccccssssaaaa"""" aaaauuuutttthhhh----ttttyyyyppppeeee====""""bbbbaaaassssiiiicccc"""" ddddbbbbmmmm====""""////uuuussssrrrr////nnnnssss----hhhhoooommmmeeee////uuuusssseeeerrrrddddbbbb////SSSSiiiitttteeeeMMMMggggrrrr"""" PPPPaaaatttthhhhCCCChhhheeeecccckkkk ffffnnnn====""""rrrreeeeqqqquuuuiiiirrrreeee----aaaauuuutttthhhh"""" rrrreeeeaaaallllmmmm====""""ssssmmmmCCCCGGGGIIII"""" aaaauuuutttthhhh----ttttyyyyppppeeee====""""bbbbaaaassssiiiicccc"""" <<<<////OOOObbbbjjjjeeeecccctttt>>>> <<<<OOOObbbbjjjjeeeecccctttt ppppppppaaaatttthhhh====""""////vvvvaaaarrrr////wwwwwwwwwwww////ccccggggiiii----bbbbiiiinnnn////ssssmmmmddddbbbbffff....****"""">>>> AAAAuuuutttthhhhTTTTrrrraaaannnnssss ffffnnnn====""""bbbbaaaassssiiiicccc----nnnnccccssssaaaa"""" aaaauuuutttthhhh----ttttyyyyppppeeee====""""bbbbaaaassssiiiicccc"""" ddddbbbbmmmm====""""////uuuussssrrrr////nnnnssss----hhhhoooommmmeeee////uuuusssseeeerrrrddddbbbb////SSSSiiiitttteeeeMMMMggggrrrr"""" PPPPaaaatttthhhhCCCChhhheeeecccckkkk ffffnnnn====""""rrrreeeeqqqquuuuiiiirrrreeee----aaaauuuutttthhhh"""" rrrreeeeaaaallllmmmm====""""ssssmmmmddddbbbbCCCCGGGGIIII"""" aaaauuuutttthhhh----ttttyyyyppppeeee====""""bbbbaaaassssiiiicccc"""" <<<<////OOOObbbbjjjjeeeecccctttt>>>> - 6 - <<<<OOOObbbbjjjjeeeecccctttt ppppppppaaaatttthhhh====""""////vvvvaaaarrrr////wwwwwwwwwwww////ccccggggiiii----bbbbiiiinnnn////ssssiiiitttteeeessssttttaaaatttt....****"""">>>> AAAAuuuutttthhhhTTTTrrrraaaannnnssss ffffnnnn====""""bbbbaaaassssiiiicccc----nnnnccccssssaaaa"""" aaaauuuutttthhhh----ttttyyyyppppeeee====""""bbbbaaaassssiiiicccc"""" ddddbbbbmmmm====""""////uuuussssrrrr////nnnnssss----hhhhoooommmmeeee////uuuusssseeeerrrrddddbbbb////SSSSiiiitttteeeeMMMMggggrrrr"""" PPPPaaaatttthhhhCCCChhhheeeecccckkkk ffffnnnn====""""rrrreeeeqqqquuuuiiiirrrreeee----aaaauuuutttthhhh"""" rrrreeeeaaaallllmmmm====""""ssssmmmmCCCCGGGGIIII"""" aaaauuuutttthhhh----ttttyyyyppppeeee====""""bbbbaaaassssiiiicccc"""" <<<<////OOOObbbbjjjjeeeecccctttt>>>> +o Optionally, if you wish to deny access to the underlying RCS directories and files (when using version control in SiteMgr), add the following lines (to the same file, _o_b_j._c_o_n_f): <<<<OOOObbbbjjjjeeeecccctttt ppppppppaaaatttthhhh====""""****////RRRRCCCCSSSS////****"""">>>> PPPPaaaatttthhhhCCCChhhheeeecccckkkk ffffnnnn====ddddeeeennnnyyyy----eeeexxxxiiiisssstttteeeennnncccceeee SSSSeeeerrrrvvvviiiicccceeee ffffnnnn====sssseeeerrrrvvvveeeerrrr----rrrreeeettttrrrriiiieeeevvvveeee <<<<////OOOObbbbjjjjeeeecccctttt>>>> If you are using a NCSA 1.5.x or Apache 1.x server, put this in conf/access.conf to achieve the same result: <<<<DDDDiiiirrrreeeeccccttttoooorrrryyyy ////****////RRRRCCCCSSSS////****>>>> <<<<LLLLiiiimmmmiiiitttt GGGGEEEETTTT PPPPUUUUTTTT PPPPOOOOSSSSTTTT>>>> oooorrrrddddeeeerrrr aaaalllllllloooowwww,,,,ddddeeeennnnyyyy ddddeeeennnnyyyy ffffrrrroooommmm aaaallllllll <<<<////LLLLiiiimmmmiiiitttt>>>> <<<<////DDDDiiiirrrreeeeccccttttoooorrrryyyy>>>> +o Restart your HTTP server instance. 2.6.3 _L_o_g__A_n_a_l_y_s_i_s__v_i_a__S_i_t_e_M_g_r To fully utilize SiteMgr's log analysis features, you may need to modify your HTTP server's logging configuration variables. +o For a NCSA 1.5.x or Apache 1.x server, most of the available logging directives will work fine with SiteMgr. You should have an entry like one of the following in conf/httpd.conf. SiteMgr prefers the "Combined" option. LLLLooooggggOOOOppppttttiiiioooonnnnssss SSSSeeeeppppaaaarrrraaaatttteeee LLLLooooggggOOOOppppttttiiiioooonnnnssss CCCCoooommmmbbbbiiiinnnneeeedddd LLLLooooggggOOOOppppttttiiiioooonnnnssss DDDDaaaatttteeee In particular, the log file format has an impact on the statistics visualization feature of SiteMgr. If the logs are combined, the referrer and the access information can be synthesized to graphically show hits from one local document to another. If they are separated, the origin of a hit cannot be displayed in - 7 - the animated view. +o For a Netscape 2.x server, use the Netscape Admin Server to set the Server Status->Log Preferences format. Select the "Only log" option and check the top eight options. Your form should look like this: FFFFoooorrrrmmmmaaaatttt:::: <<<< >>>> UUUUsssseeee CCCCoooommmmmmmmoooonnnn LLLLooooggggffffiiiilllleeee FFFFoooorrrrmmmmaaaatttt <<<<xxxx>>>> OOOOnnnnllllyyyy lllloooogggg:::: [[[[xxxx]]]] CCCClllliiiieeeennnntttt hhhhoooossssttttnnnnaaaammmmeeee [[[[xxxx]]]] AAAAuuuutttthhhheeeennnnttttiiiiccccaaaatttteeee uuuusssseeeerrrr nnnnaaaammmmeeee [[[[xxxx]]]] SSSSyyyysssstttteeeemmmm ddddaaaatttteeee [[[[xxxx]]]] FFFFuuuullllllll rrrreeeeqqqquuuueeeesssstttt [[[[xxxx]]]] SSSSttttaaaattttuuuussss [[[[xxxx]]]] CCCCoooonnnntttteeeennnntttt lllleeeennnnggggtttthhhh [[[[xxxx]]]] HHHHTTTTTTTTPPPP hhhheeeeaaaaddddeeeerrrr,,,, """"rrrreeeeffffeeeerrrrrrrreeeerrrr"""" [[[[xxxx]]]] HHHHTTTTTTTTPPPP hhhheeeeaaaaddddeeeerrrr,,,, """"uuuusssseeeerrrr----aaaaggggeeeennnntttt"""" [[[[ ]]]] MMMMeeeetttthhhhoooodddd [[[[ ]]]] UUUURRRRIIII [[[[ ]]]] QQQQuuuueeeerrrryyyy ssssttttrrrriiiinnnngggg ooooffff tttthhhheeee UUUURRRRIIII [[[[ ]]]] PPPPrrrroooottttooooccccoooollll If your Netscape Admin Server insists that you rename your access log file, you can move the existing access log file (while the server is stopped) and then modify the log preferences. +o Restart your HTTP server instance. Be sure that your HTTP server has sufficient file read/write permissions to update the log files. +o You may find it necessary to rename your access log file. Keep in mind that the SiteMgr server looks for a file named _a_c_c_e_s_s or _a_c_c_e_s_s__l_o_g in your log directory. 2.7 _E_x_e_c_u_t_i_o_n__A_f_t_e_r__I_n_s_t_a_l_l_a_t_i_o_n After the software has been installed, you might want to force your shell to re-cache its list of known executables: %%%% rrrreeeehhhhaaaasssshhhh You can then execute the SiteMgr client. It is found in /_u_s_r/_s_b_i_n/_s_i_t_e_m_g_r, and can be started from a shell: %%%% ssssiiiitttteeeemmmmggggrrrr You can also launch SiteMgr by double-clicking on the "sitemgr" icon found in the WebTools page of the icon - 8 - catalog or the use the File "Find" tool to locate the icon. The client application process places itself in the background by default.